Systems, methods, and non-transitory computer readable mediums for dynamic selection of advanced approach procedures

ABSTRACT

Systems and methods, and non-transitory computer readable mediums directed to generating an adaptive glide slope angle and allowing a pilot to interact with the generated glide slope angle are provided. The systems and methods, and non-transitory computer readable mediums retrieve, from a navigation database (NDB), a designated approach procedure for the aircraft, and identify a designated glide slope angle (D_GSA) based thereon. The systems and methods, and non-transitory computer readable mediums receive sensed actual weather data and sensed aircraft status data and generate an adaptive glide slope angle A_GSA based thereon. The systems and methods, and non-transitory computer readable mediums allow modification of and modify, or prevent modification of, the designated approach procedure with the A_GSA based on the determination of whether or not the A_GSA is compatible with the designated approach procedure.

TECHNICAL FIELD

The technical field generally relates to aircraft guidance systems, andmore particularly relates to systems and related operating methods fordynamic selection of advanced approach procedures.

BACKGROUND

The phase of flight prior to landing an aircraft is referred to as“approach,” or an approach procedure. Conventionally, each runway orlanding area has for it a designated approach procedure, which is apre-published set of maneuvers that a pilot follows. The designatedapproach procedure includes a designated glide slope angle for anaircraft to follow in its final approach segment.

In order to increase capacity at airports, advanced approach proceduresthat increase the published glide slope angle are often desirable. Anincreased glide slope angle may also provide the benefit of reducing animpact on the environment (noise and emissions) over conventionalapproach systems. However, the glide slope angle cannot automatically beincreased in all cases because conditions may exist around the landingdestination or aircraft that would restrict such an increase. Therefore,advanced approach procedures capable of generating, in real time, a safeadaptation to the published glide slope angle and allowing a pilot tointeractively choose it are desirable. The following disclosure providesthese technological enhancements over systems employing conventionalapproach procedures, in addition to addressing related issues.

BRIEF SUMMARY

This summary is provided to describe select concepts in a simplifiedform that are further described in the Detailed Description. Thissummary is not intended to identify key or essential features of theclaimed subject matter, nor is it intended to be used as an aid indetermining the scope of the claimed subject matter.

Provided is a method to be carried out by an onboard system of anaircraft, the onboard system including a display device and a userinterface. The method comprising: in a control module, receiving, viathe user interface, a selection of a designated approach procedure in aflight plan; retrieving, from a navigation database (NDB), thedesignated approach procedure; identifying a designated glide slopeangle (D_GSA) based on the designated approach procedure; determining anadaptive glide slope angle (A_GSA) based on data from an on-board sensorsystem; determining whether or not the A_GSA is compatible with thedesignated approach procedure; displaying the D_GSA and A_GSA on thedisplay device, enabling the pilot to utilize the user interface tomodify the designated approach procedure with the A_GSA, when thedesignated approach procedure is compatible with the A_GSA; and barringmodification of the designated approach procedure with the A_GSA, andgenerating a first alert, when the A_GSA is not compatible with thedesignated approach procedure, and allowing modification of thedesignated approach procedure with the A_GSA when the A_GSA iscompatible with the designated approach procedure.

Also provided is a system for an approach procedure for an aircraft, thesystem comprising: a display system; a control module coupled to thedisplay system, the control module comprising a processor and a memorydevice, the control module configured to: receive, from a userinterface, a user selected designated approach procedure for theaircraft; retrieve, from a navigation database (NDB), the designatedapproach procedure; identify a designated glide slope angle (D_GSA)based on the designated approach procedure; receive sensed data from anon-board sensor system; determine an adaptive glide slope angle (A_GSA)based the sensed data; process the A_GSA with the designated approachprocedure to determine whether or not the A_GSA is compatible with thedesignated approach procedure; and command the display device to rendera user interface comprising a plurality of icons, the plurality of iconscomprising, a first icon indicating the D_GSA, a second icon indicatingthe A_GSA, and a third icon indicating whether or not the A_GSA iscompatible with the designated approach procedure.

Another method for an approach procedure for an aircraft is provided.The method comprising: at a control module: receiving a user designatedapproach procedure, altitude constraints, and landing parameters;retrieving, from a navigation database (NDB) the designated approachprocedure; identifying a designated glide slope angle (D_GSA) based onthe designated approach procedure; receiving sensed weather data andsensed aircraft status data from an on-board sensor system; determiningan adaptive glide slope angle (A_GSA) based the sensed weather data andthe sensed aircraft status data; processing the A_GSA with thedesignated approach procedure to determine whether or not the A_GSA iscompatible with the designated approach procedure; and commanding adisplay device to render a user interface comprising a plurality oficons, the plurality of icons comprising, a first icon indicating theD_GSA, a second icon indicating the A_GSA, and a third icon indicatingwhether or not the A_GSA is compatible with the designated approachprocedure.

Furthermore, other desirable features and characteristics of the systemand method will become apparent from the subsequent detailed descriptionand the appended claims, taken in conjunction with the accompanyingdrawings and the preceding background.

BRIEF DESCRIPTION OF THE DRAWINGS

The present application will hereinafter be described in conjunctionwith the following drawing figures, wherein like numerals denote likeelements, and:

FIG. 1 is a functional block diagram illustrating an adaptiveinteractive glide slope angle system, in accordance with variousexemplary embodiments;

FIG. 2 is an illustration of a generated adaptive glide slope angle, inaccordance with various exemplary embodiments;

FIG. 3 is an illustration showing a level segment introduced by agenerated adaptive glide slope angle, in accordance with variousexemplary embodiments;

FIG. 4 is a display image for a user interface illustrating an adaptiveglide slope angle being determined as compatible with a final approach,in accordance with various exemplary embodiments;

FIG. 5 is a display image for a user interface illustrating an adaptiveglide slope angle being determined as incompatible with a finalapproach, in accordance with various exemplary embodiments; and

FIG. 6 is a flow chart describing a method for providing an adaptiveinteractive glide slope angle, in accordance with various exemplaryembodiments.

DETAILED DESCRIPTION

The following detailed description is merely illustrative in nature andis not intended to limit the embodiments of the subject matter or theapplication and uses of such embodiments. As used herein, the word“exemplary” means “serving as an example, instance, or illustration.”Thus, any embodiment described herein as “exemplary” is not necessarilyto be construed as preferred or advantageous over other embodiments. Allof the embodiments described herein are exemplary embodiments providedto enable persons skilled in the art to make or use the invention andnot to limit the scope of the invention that is defined by the claims.Furthermore, there is no intention to be bound by any expressed orimplied theory presented in the preceding technical field, background,brief summary, or the following detailed description.

As used herein, the term module refers to any hardware, software,firmware, electronic control component, processing logic, and/orprocessor device, individually or in any combination, including withoutlimitation: application specific integrated circuit (ASIC), anelectronic circuit, a processor (shared, dedicated, or group) and memorythat executes one or more software or firmware programs, a combinationallogic circuit, and/or other suitable components that provide thedescribed functionality. The provided system and method may take theform of a control module, and may be separate from, or integratedwithin, a preexisting mobile platform management system or aircraftflight management system (FMS).

As an overview, the disclosed control module processes current actualweather data and current aircraft conditions to generate an adaptiveglide slope angle, which may be a slight angular change to the publishedglide slope angle. The control module retrieves a designated glide slopeangle, as well as other relevant constraints around the airport orlanding area, such as altitude and terrain constraints. The controlmodule executes novel rules encoded in memory to determine whether theadaptive glide slope angle is compatible with the designated approachprocedure. Responsive the determination of compatibility, the controlmodule either allows modification of the designated approach procedurein accordance with the adaptive glide slope angle, or generates an alertand bars or does not allow the designated glide slope angle to bemodified. Although the depicted control module is generally realizedwithin an aircraft, for example, as part of a flight management system,the concepts presented here can be adapted to a variety of mobileplatforms, such as vehicles, spacecraft, watercraft, and the like. Thefigures and descriptions below provide more detail.

Turning now to FIG. 1, a functional block diagram of an aircraft 100with an adaptive interactive glide slope angle system (AIGSA system 102)is depicted, in accordance with various exemplary embodiments. In thedepicted embodiment, the AIGSA system 102 includes: a control module104, operationally coupled to a transceiver 108, a user input device110, a display system 112, and an on-board sensor system 114. The AIGSAsystem 102 also receives wireless signals 105, comprising traffic data,air traffic control (ATC) commands, weather reports, and etc.

In various embodiments, wireless signals 105 may comprise wirelesssignals from a variety of different combinations of wireless sources106. Wireless sources 106 may comprise any combination of, a datalinkand air traffic control (ATC) system, an electronic flight bag(EFB)/electronic ground proximity warning system (EGPWS), a trafficcollision and avoidance system (TCAS), a weather information system, andother systems as conventionally known to persons of skill in the art.

The transceiver 108 enables the control module 104 to establish andmaintain the communications links between the control module 104, otheronboard components, and the wireless sources 106. The transceiver 108may include at least one receiver and at least one transmitter that areoperatively coupled to the control module 104. The transceiver 108 cansupport wired and a variety of types of wireless communication, and canperform signal processing (e.g., digitizing, data encoding, modulation,etc.) as is known in the art. In some embodiments, the transceiver 108is integrated with the control module 104.

In various embodiments, the user input device 110 may include any one,or combination, of various known user input device devices including,but not limited to: a touch sensitive screen; a cursor control device(CCD) (not shown), such as a mouse, a trackball, or joystick; akeyboard; one or more buttons, switches, or knobs; a voice input system;and a gesture recognition system. Non-limiting examples of uses for theuser input device 110 include: entering values for stored variables 164,loading or updating instructions and applications 160, and loading andupdating the contents of the database 156, each described in more detailbelow. Users may enter data and information such as, selection of adesignated approach procedure, flight plan, and landing parameters viathe user input device 110.

The display system 112 may be implemented using any one of numerousknown display devices suitable for rendering textual, graphic, and/oriconic information in a format viewable by a user. The display devicesmay provide three dimensional or two dimensional images, and may providesynthetic vision imaging. Non-limiting examples of such display devicesinclude cathode ray tube (CRT) displays, and flat panel displays such asLCD (liquid crystal displays) and TFT (thin film transistor) displays.Accordingly, each display device responds to a communication protocolthat is either two- or three-dimensional, and may support the overlay oftext, alphanumeric information, or visual symbology. The displaydevice(s) in the display system 112 may each, individually, beresponsive to user input via user input device(s) 110 and/or be underthe control of the control module 104. In various embodiments, such astouch screen display systems, the display system 112 and the user inputdevice 110 are integrated.

The on-board sensor system 114 may comprise any combination of sensingdevices. The on-board sensor system 114 comprises weather sensors 120that provide “actual weather” which is current, or real-time, sensedweather data, such as temperature, wind velocity and direction,humidity, precipitation, etc. The on-board sensor system 114 alsocomprises aircraft system and subsystem status sensors 122 (whichincludes sensors and means for detecting fuel level, engine temperature,aircraft type and weight class, engine thrust, the status of brakes, andthe like). Specifically, the aircraft system and subsystem statussensors 122 also comprise a geographic positioning system (GPS). Theon-board sensor system 114 may further comprise a means for convertingthe various sensed temperatures, pressures, conductivities, and thelike, into electrical signals for processing by the control module 104.

Referring again to FIG. 1, within the AIGSA system 102, the controlmodule 104 performs the functions of the AIGSA system 102. The controlmodule 104 comprises a processor 150 and a memory 152. The controlmodule 104 also includes an interface 154, communicatively coupled tothe processor 150 and the memory 152 (via a bus 155), a database 156,and an optional storage disk 158. The processor 150 may comprise anytype of processor or multiple processors, single integrated circuitssuch as a microprocessor, or any suitable number of integrated circuitdevices and/or circuit boards working in cooperation to carry out thedescribed operations, tasks, and functions by manipulating electricalsignals representing data bits at memory locations in the system memory,as well as other processing of signals.

In operation, the processor 150 may utilize one or more computerreadable storage media, such as a memory 152, the database 156, and adisk 158 for storage and a scratch pad. The memory locations where databits are maintained in computer readable storage media are physicallocations that have particular electrical, magnetic, optical, ororganic, properties corresponding to the data bits. The memory 152 canbe any type of suitable computer readable storage medium. For example,the memory 152 may include various types of dynamic random access memory(DRAM) such as SDRAM, the various types of static RAM (SRAM), and thevarious types of non-volatile memory (PROM, EPROM, and flash). Incertain examples, the memory 152 is located on and/or co-located on thesame computer chip as the processor 150. In the depicted embodiment, thememory 152 stores the above-referenced instructions and applications 160along with one or more configurable variables in stored variables 164.

The database 156 is a computer readable storage medium in the form ofany suitable type of storage apparatus, including direct access storagedevices such as hard disk drives, flash systems, floppy disk drives andoptical disk drives. As used herein, the database 156 comprises anavigation database (NDB) as known in the art. Information in thedatabases 156 may be preloaded, and/or organized or imported during aninitialization step (for example, at 602 of the method 600 in FIG. 6).

The bus 155 serves to transmit programs, data, status and otherinformation or signals between the various components of the controlmodule 104. The bus 155 can be any suitable physical or logical means ofconnecting computer systems and components. This includes, but is notlimited to, direct hard-wired connections, fiber optics, infrared andwireless bus technologies. During operation, the AIGSA program 162,stored in the memory 152, is loaded and executed by the processor 150.

The interface 154 enables communications within the Control module 104,can include one or more network interfaces to communicate with othersystems or components, and can be implemented using any suitable methodand apparatus. For example, the interface 154 enables communication froma system driver and/or another computer system. In one embodiment, theinterface 154 obtains the various wireless signals 105 from wirelesssource 106 directly. The interface 154 may also include one or morenetwork interfaces to communicate with technicians, and/or one or morestorage interfaces to connect to storage apparatuses, such as thedatabase 156.

During operation, the processor 150 loads and executes one or moreprograms, algorithms and rules embodied as instructions and applications160 contained within the memory 152 and, as such, controls the generaloperation of the AIGSA system 102. Accordingly, the processor 150 isconfigured to process received inputs (any combination of: the userinput provided via the user input device 110, wireless signals 105 fromwireless sources 106, and sensed information from the on-board sensorsystem 114), reference the database 156 in accordance with the AIGSAprogram 162, and command and control the display system 112 basedthereon.

With specific focus on approach procedures, the processor 150 and thememory 152 of the control module 104 form an adaptive glideslope enginethat performs the processing activities. The adaptive glideslope engineprovides a technological improvement to the conventional display of, andcontrol over, glideslope angle implementation, in part, by determiningan adaptive glide slope angle and enabling a dynamic selection of theadaptive glide slope angle. The control module 104 thereby realizes anunconventional technological improvement to conventional continuousdescent operations, such as approach procedures. The adaptive glideslopeengine performs the processing activities, such as the method 600 ofFIG. 6, in accordance with the AIGSA program 162, as is described inmore detail below.

It will be appreciated that AIGSA system 102 may differ from theembodiment depicted in FIG. 1. As a first example, in variousembodiments, any combination of the user input device 110, thetransceiver 108, and the display system 112 can be integrated, forexample, as part of an existing FMS or cockpit display in an aircraft.In another example, the on-board sensor system 114 may bedis-integrated, and comprise multiple sensor systems distributed aroundthe aircraft and interacting individually with the control module 104.Regardless of the state of integration of these systems, a user maycontrol one or more features of the AIGSA system 102 by providing userinput via at least the user input device 110.

Turning now to FIG. 2 and FIG. 3, some relevant measurements andfeatures are depicted and described. Aircraft 100 is in its finalapproach segment, following a designated approach procedure on a path204 to an intersection point 206 on a landing threshold of a runway 208.It is understood that the landing threshold may extend perpendicularlyacross a width of the runway 208, and the intersection point 206 is ageneralized spot on the landing threshold at which the aircraft 100 willfirst make contact with the runway 208. The designated approachprocedure has a designated glide slope angle D_GSA 210. As mentioned,the control module 104 processes data from the on-board sensor system114 (sensed actual/current weather data from weather sensors 120 andsensed current aircraft status data from status sensors 122), andgenerates an adaptive glide slope angle A_GSA 212 based thereon. Inoperation, taking advantage of the A_GSA 212 means moving the aircraft100 from its path 204 to path 214, which is visibly steeper (i.e., therise over run is larger) than path 204. Path 214 is also heading towardthe intersection point 206 on the landing threshold of the runway 208.In various embodiments, A_GSA is less than or equal to plus 3.5 degreesof the D_GSA.

After determining the A_GSA 212, the control module 104 determineswhether or not the A_GSA is compatible with the designated approachprocedure before making the A_GSA an available and selectable option forthe pilot. In various embodiments, a determination that the A_GSA is notcompatible with the designated approach procedure comprises determiningthat one or more conditions are violated (conditions are describedbelow). Also, in various embodiments, the results of the determinationof whether the A_GSA is compatible with the designated approachprocedure may be communicated to air traffic control (ATC) for use indescent planning. If one or more of the conditions is violated, thecontrol module 104 does not allow modification of the final approachsegment (i.e., it may not be changed from 204 to 214).

In a first example condition, the control module 104 does not allowmodification of the designated approach procedure with the A_GSA if theposition and location of the aircraft 100 at the time of thedetermination violates (is less than or equal to) a predetermineddistance 220 from the landing threshold. Said differently, the aircraftis too close to the landing threshold to make the change. If theposition and location of the aircraft 100 at the time of thedetermination greater than the predetermined distance 220 from thelanding threshold, the predetermined distance is not violated. Arrow 222indicates the region in which the aircraft 100 position and location atthe time of the determination is greater than a predetermined distance220 from the landing threshold, i.e. the aircraft is not in violation ofthe predetermined distance 220 and modification of the designatedapproach procedure with the A_GSA is allowed.

In another example condition, the position and location of the aircraft100, in addition to its ground speed, is processed. In this example,determining that the A_GSA is not compatible with the designatedapproach procedure comprises determining that an amount of time beforelanding based on the aircraft position, location, and ground speed, isless than a predetermined amount of time before landing. Similar to theabove, this means that there is just not enough time to enact the changebefore landing. The aforementioned predetermined distance andpredetermined amount of time may be configurable variables that arepredetermined and stored in stored variables 164, or they may be basedon the designated approach procedure.

A third condition involves an altitude constraint. When the aircraftchanges its flight path from path 204 to path 214, the flight profilemay look something like the illustration 300 of FIG. 3. A lateralsegment is introduced as aircraft 100 flies from a point 302 to point304, from which point it may take path 214 to the runway 208. Thelateral segment from point 302 to point 304 is at altitude 306 aboveground. In some scenarios, such as continuous descent operations, finalapproach segment altitude constraints do not permit lateral segments.For example, altitude constraints or restrictions may be in place atlocation 308 or at altitude 306. The control module 104 may find finalapproach segment altitude constraints in the NDB in database 156. Whenan existing altitude constraint does not permit the lateral segment from302 to 304, the control module 104 does not allow use of the generatedA_GSA.

In various embodiments, upon determining that that the A_GSA is notcompatible with the designated approach procedure, the control module104 does not allow modification of the designated approach procedurewith the A_GSA. In addition, the control module 104 may also generate analert. The alert may be a rendered on an image or interactive userinterface on the display system 112, and may employ any of various knownvisually distinguishing techniques, such as text changes, color changes,highlighting, blinking, and the like.

A non-limiting example of an interactive user interface that may berendered on the display system 112 is depicted in FIGS. 4 and 5. Theexemplary user interface has a plurality of icons arranged in a patternto facilitate intuitive interaction with the AIGSA system 102. Theplurality of icons comprises a first icon 502 indicating the D_GSA witha respective value (3 degrees in FIG. 4 and FIG. 5); a second icon 504indicating the A_GSA and a respective value (3.2 degrees in FIG. 4 andFIG. 5); a third icon 506 indicating whether or not the A_GSA iscompatible with the designated approach procedure; a fourth icon (508)indicating whether or not the AIGSA system 102 is activated; a fifthicon (510) indicating an approach type, a sixth icon (512) indicatingthe final approach segment altitude constraint, and a seventh icon (514)providing an option to activate the A_GSA system 102. The approach typeand the final approach segment altitude constraint may be received aheadof time and stored in memory 152, or may be based on processing thedesignated approach procedure.

On comparison of FIG. 4 and FIG. 5, it is observable that in FIG. 4, theA_GSA is compatible with the approach procedure (FIG. 4, 506), whereasin FIG. 5, it is not (FIG. 5, 506). Accordingly, the option to activatethe AIGSA system 102 (seventh icon 514) is available in FIG. 4 andfourth icon 508 indicates with text that it has been activated, whereasin FIG. 5, the seventh icon (514) indicates with a lack of text (dashes)that there's no option to activate the AIGSA system 102, and the fourthicon (508) shows that the AIGSA system 102 is not activated. Further, itis understood that the control module 104 receives user input toactivate the AIGSA system 102 subsequent to indicating that the optionto activate the AIGSA system 102 is allowed, and the control module 104receives user input to modify the designated approach procedure with theA_GSA subsequent to indicating that the option to modify the designatedapproach procedure with the A_GSA is allowed. In each case, the controlmodule 104 capably determines that the user input has been receivedsubsequent to the respective prompt, such as the icon indicating thatthe A_GSA is compatible with the approach procedure (third icon 506).

As mentioned, the processor 150 and the AIGSA program 162 form anadaptive interactive glide slope angle (AIGSA) engine that continually,and in real time, generates the A_GSA, and processes the sensed datafrom the sensor system 114 in accordance with a set of rules encoded inthe AIGSA program 162. Referring now to FIG. 6 and with continuedreference to FIGS. 1-5, a flow chart is provided for a method 600 forproviding an AIGSA, in accordance with various exemplary embodiments.Method 600 represents various embodiments of a method associated forproviding an interactive adaptive glide slope angle. For illustrativepurposes, the following description of method 600 may refer to elementsmentioned above in connection with FIG. 1. In practice, portions ofmethod 600 may be performed by different components of the describedsystem. It should be appreciated that method 600 may include any numberof additional or alternative tasks, the tasks shown in FIG. 6 need notbe performed in the illustrated order, and method 600 may beincorporated into a more comprehensive procedure or method havingadditional functionality not described in detail herein. Moreover, oneor more of the tasks shown in FIG. 6 could be omitted from an embodimentof the method 600 as long as the intended overall functionality remainsintact.

The method starts, and at 602 the control module 104 is initialized. Asmentioned above, initialization may comprise uploading or updatinginstructions and applications 160, AIGSA program 162, stored variables164, and the various lookup tables stored in the database 156.Predetermined variables may include, for example, predetermineddistances and times to use as thresholds, parameters for setting up auser interface that is displayed (for example 500), and the variousshapes, various colors and/or visually distinguishing techniques usedfor icons and alerts. In an embodiment, at 602, the method 600initializes navigational map data in the database 156. In someembodiments, AIGSA program 162 includes additional instructions andrules for rendering information differently based on type of displaydevice in display system 112. Initialization at 602 may also includeidentifying wireless sources 106 and/or wireless signals 105.

At 603 user designations or selections are received. The user maydesignate one or more of: an approach procedure, flight plan, altitudeconstraints, and landing parameters. At 604 the designated approachprocedure is retrieved from the NDB (database 156), based on the userselections. The designated approach procedure is generally airport orlanding area specific, and may comprise additional constraints, such asaltitude constraints and/or ground distance constraints and flightconstraints around obstacles or environmental features. At 606, a glideslope angle associated with the designated approach procedure isidentified. This glide slope angle is referred to as a designated glideslope angle D_GSA 210, and is the default glide slope angle unless anduntil modified later. At 608 sensed data from an on-board sensor system114 is processed by the control module 104, and an adaptive glide slopeangle A_GSA is determined therefrom The sensed data may include sensedactual weather data from weather sensors 120, and sensed aircraft statusdata from status sensors 122. The sensed aircraft status data maycomprise static status data, such as an aircraft identification andweight class, as well as dynamic status data, such as fuel levels,engine temperatures, aircraft ground speed, aircraft position andlocation, dynamically calculated aircraft weight based on, for example,fuel consumption, aircraft altitude, and the like. At any time, theaircraft ground speed and position and location may be processed todetermine a descent rate.

At 609, the method determines whether the A_GSA is steeper than theD_GSA. Typically, the A_GSA is between three and three and a halfdegrees steeper than the D_GSA. If it is steeper, at 611, the A_GSA isdisplayed on the display system 112. At 613, the method evaluates thefinal approach segment with A_GSA.

At 610, the method 600 determines whether or not the generated A_GSA iscompatible with the existing approach procedure. The determination at610 may comprise comparing various sensed data to information providedin the designated approach procedure. As mentioned above, the violationof conditions such as altitude constraints, distance to landing and timeto landing are determined in the process of determining whether or notthe generated A_GSA is compatible with the existing approach procedure.Performing these condition checks increase safety and confidence inmodifying the designated approach procedure. Upon determining that theA_GSA is compatible with the designated approach procedure at 610, themethod proceeds to allowing modification of the designated approachprocedure with the A_GSA at 616. 616 may include prompting a user (witha rendering on the display system 112) that the approach is compatible,further prompting the user to activate the A_GSA system, and furtherdisplaying when the A_GSA system is activated. When the user thenselects modification of the designated approach procedure eith theA_GSA, the method generates an aircraft descent trajectory using theA_GSA. At 622, the display system 112 updates displayed images toreflect the user selections and modifications.

At 612, when it is determined that the generated A_GSA is not compatiblewith the existing approach procedure, the method 600 may preventmodification of the approach procedure with the A_GSA. Referring againto FIG. 5, in various embodiments, the A_GSA that has been calculatedmay be on display on the user interface (see icon 504), however, theoption to activate the AIGSA system to utilize the A_GSA may beprevented (see icon 514). In various embodiments, the manner in whichthe fact that it is prevented, or disallowed from use, is indicated mayinvolve one or more techniques for visually distinguishing the fourthicon (see FIG. 6, icon 514 in which it uses dashes). In otherembodiments, the method may include displaying text stating that theoption is not available. Accordingly at 612, the glide slope angle usedis restricted to the published D_GSA (see FIG. 6, icon 502). At 612, orin a separate method step, such as at 614, a first alert may begenerated to draw the pilot's attention to the incompatibility of theA_GSA with the designated approach procedure.

In addition to the above checks of conditions, at 618 variousembodiments may further compare D_GSA to the A_GSA, and if the D_GSA isgreater than or equal to the A_GSA, a second alert may be generated at620. The second alert is rendered in a manner that is visually distinctfrom the first alert. The reason for the second alert is to draw thepilot's attention to the fact that, upon comparing actual weatherconditions and actual aircraft status, a more gradual glide slope angleis recommended (A_GSA being smaller than D_GSA). From 614, the processmay return to 608 and determine another A_GSA. After 622, the method 600may end. Transitioning away from an alert such as at 620 or at 614 maybe conditioned upon receiving a user acknowledgment, and the useracknowledgment may trigger the de-asserting of the second alert, and insome cases, also the first alert.

As is readily appreciated, the above examples of the adaptiveinteractive glide slope angle system (AIGSA system 102) arenon-limiting, and many others may be addressed by the control module104. Thus, systems and methods directed to improvements in thepresentation and use of glide slope angles during approach overconventional guidance systems are provided.

Those of skill in the art will appreciate that the various illustrativelogical blocks, modules, circuits, and algorithm steps described inconnection with the embodiments disclosed herein may be implemented aselectronic hardware, computer software, or combinations of both. Some ofthe embodiments and implementations are described above in terms offunctional and/or logical block components (or modules) and variousprocessing steps. However, it should be appreciated that such blockcomponents (or modules) may be realized by any number of hardware,software, and/or firmware components configured to perform the specifiedfunctions. To clearly illustrate the interchangeability of hardware andsoftware, various illustrative components, blocks, modules, circuits,and steps have been described above generally in terms of theirfunctionality. Whether such functionality is implemented as hardware orsoftware depends upon the particular application and design constraintsimposed on the overall system. Skilled artisans may implement thedescribed functionality in varying ways for each particular application,but such implementation decisions should not be interpreted as causing adeparture from the scope of the present invention. For example, anembodiment of a system or a component may employ various integratedcircuit components, e.g., memory elements, digital signal processingelements, logic elements, look-up tables, or the like, which may carryout a variety of functions under the control of one or moremicroprocessors or other control devices. In addition, those skilled inthe art will appreciate that embodiments described herein are merelyexemplary implementations.

The various illustrative logical blocks, modules, and circuits describedin connection with the embodiments disclosed herein may be implementedor performed with a general purpose processor, a digital signalprocessor (DSP), an application specific integrated circuit (ASIC), afield programmable gate array (FPGA) or other programmable logic device,discrete gate or transistor logic, discrete hardware components, or anycombination thereof designed to perform the functions described herein.A general-purpose processor may be a microprocessor, but in thealternative, the processor may be any conventional processor,controller, microcontroller, or state machine. A processor may also beimplemented as a combination of computing devices, e.g., a combinationof a DSP and a microprocessor, a plurality of microprocessors, one ormore microprocessors in conjunction with a DSP core, or any other suchconfiguration.

The steps of a method or algorithm described in connection with theembodiments disclosed herein may be embodied directly in hardware, in asoftware module executed by a controller or processor, or in acombination of the two. A software module may reside in RAM memory,flash memory, ROM memory, EPROM memory, EEPROM memory, registers, harddisk, a removable disk, a CD-ROM, or any other form of storage mediumknown in the art. An exemplary storage medium is coupled to theprocessor such that the processor can read information from, and writeinformation to, the storage medium. In the alternative, the storagemedium may be integral to the processor. The processor and the storagemedium may reside in an ASIC.

In this document, relational terms such as first and second, and thelike may be used solely to distinguish one entity or action from anotherentity or action without necessarily requiring or implying any actualsuch relationship or order between such entities or actions. Numericalordinals such as “first,” “second,” “third,” etc. simply denotedifferent singles of a plurality and do not imply any order or sequenceunless specifically defined by the claim language. The sequence of thetext in any of the claims does not imply that process steps must beperformed in a temporal or logical order according to such sequenceunless it is specifically defined by the language of the claim. Theprocess steps may be interchanged in any order without departing fromthe scope of the invention as long as such an interchange does notcontradict the claim language and is not logically nonsensical.

Furthermore, depending on the context, words such as “connect” or“coupled to” used in describing a relationship between differentelements do not imply that a direct physical connection must be madebetween these elements. For example, two elements may be connected toeach other physically, electronically, logically, or in any othermanner, through one or more additional elements.

While at least one exemplary embodiment has been presented in theforegoing detailed description of the invention, it should beappreciated that a vast number of variations exist. It should also beappreciated that the exemplary embodiment or exemplary embodiments areonly examples, and are not intended to limit the scope, applicability,or configuration of the invention in any way. Rather, the foregoingdetailed description will provide those skilled in the art with aconvenient road map for implementing an exemplary embodiment of theinvention. It being understood that various changes may be made in thefunction and arrangement of elements described in an exemplaryembodiment without departing from the scope of the invention as setforth in the appended claims. It will also be appreciated that while thedepicted exemplary embodiment is described in the context of a fullyfunctioning computer system, those skilled in the art will recognizethat the mechanisms of the present disclosure are capable of beingdistributed as a program product with one or more types ofnon-transitory computer-readable signal bearing media used to store theprogram and the instructions thereof and carry out the distributionthereof, such as a non-transitory computer readable medium bearing theprogram 162 and containing computer instructions stored therein forcausing a computer processor (such as the processor 150) to perform andexecute the program 162. Such a program product may take a variety offorms, and the present disclosure applies equally regardless of theparticular type of computer-readable signal bearing media used to carryout the distribution. Examples of signal bearing media include:recordable media such as floppy disks, hard drives, memory cards andoptical disks, and transmission media such as digital and analogcommunication links. It will be appreciated that cloud-based storageand/or other techniques may also be utilized in certain embodiments.

What is claimed is:
 1. A method to be carried out by an onboard systemof an aircraft, the onboard system including a display device and a userinput device, the method comprising: in a control module, receiving, viathe user input device, a selection of a designated approach procedure ina flight plan; retrieving, from a navigation database (NDB), thedesignated approach procedure; identifying a designated glide slopeangle (D_GSA) based on the designated approach procedure; determining anadaptive glide slope angle (A_GSA) based on data from an on-board sensorsystem; determining whether or not the A_GSA is compatible with thedesignated approach procedure; displaying the D_GSA and A_GSA on thedisplay device,commanding the display device to render a user interfacecomprising a plurality of icons, the plurality of icons comprising: afirst icon indicating the D_GSA, a second icon indicating the A_GSA, anda third icon indicating whether or not the A_GSA is compatible with thedesignated approach procedure; enabling the a pilot of the aircraft toutilize the user input device to modify the designated approachprocedure with the A_GSA, when the designated approach procedure iscompatible with the A_GSA; and barring modification of the designatedapproach procedure with the A_GSA, and generating a first alert, whenthe A_GSA is not compatible with the designated approach procedure, andallowing modification of the designated approach procedure with theA_GSA when the A_GSA is compatible with the designated approachprocedure.
 2. The method of claim 1, wherein determining that the A_GSAis not compatible with the designated approach procedure comprisesdetermining that employing the A_GSA violates a final approach segmentaltitude constraint.
 3. The method of claim 1, wherein the data from theon-board sensor system comprises an aircraft position and location, andwherein determining that the A_GSA is not compatible with the designatedapproach procedure comprises determining that the aircraft position andlocation violates a predetermined distance from a landing threshold. 4.The method of claim 1, wherein the data from the on-board sensor systemcomprises an aircraft ground speed, and wherein determining that theA_GSA is not compatible with the designated approach procedure furthercomprises determining that an amount of time before landing based on theaircraft position, location, and ground speed, is less than apredetermined amount of time before landing.
 5. The method of claim 1,wherein the data from the on-board sensor system comprises an aircraftposition, location, and ground speed, and wherein determining that theA_GSA is not compatible with the designated approach procedure comprisesdetermining that (i) that the aircraft position and location violates apredetermined distance from a landing threshold, or (ii) an amount oftime before landing based on the aircraft position, location, and groundspeed, is less than a predetermined amount of time before landing. 6.The method of claim 5, wherein allowing modification of the designatedapproach procedure further comprises determining that the D_GSA isgreater than or equal to the A_GSA and generating a second alert.
 7. Themethod of claim 5, further comprising: subsequent to determining thatthe A_GSA is compatible with the designated approach procedure,modifying the designated approach procedure with the A_GSA responsive toreceiving a user selection to modify the designated approach procedurewith the A_GSA.
 8. The method of claim 7 1, wherein the plurality oficons further comprising: comprises commanding a display system torender a user interface comprising a plurality of icons, the pluralityof icons comprising, a first icon indicating the D_GSA, a second iconindicating the A_GSA, a third icon indicating whether or not the A_GSAis compatible with the designated approach procedure, and a fourth iconindicating whether or not an adaptive interactive glide slope angle(AIGSA) system is activated.
 9. The method of claim 7, wherein theplurality of icons further comprises a fifth icon indicating an approachtype, a sixth icon indicating the final approach segment altitudeconstraint, and a seventh icon indicating whether or not the AIGSAsystem is activated.
 10. A system for an approach procedure for anaircraft, the system comprising: a display system; a control modulecoupled to the display system, the control module comprising a processorand a memory device, the control module configured to: receive, from auser input device, a user selected designated approach procedure for theaircraft; retrieve, from a navigation database (NDB), the designatedapproach procedure; identify a designated glide slope angle (D_GSA)based on the designated approach procedure; receive sensed data from anon-board sensor system; identifying an adaptive glide slope angle(A_GSA) based on the sensed data; process the A_GSA with the designatedapproach procedure to determine whether or not the A_GSA is compatiblewith the designated approach procedure; and command the display deviceto render a user interface comprising a plurality of icons, theplurality of icons comprising, a first icon indicating the D_GSA, asecond icon indicating the A_GSA, and a third icon indicating whether ornot the A_GSA is compatible with the designated approach procedure. 11.The system of claim 10, wherein the control module is further configuredto: upon determining that the A_GSA is not compatible with thedesignated approach procedure, generate a first alert and preventmodification of the designated approach procedure with the A_GSA. 12.The system of claim 11, wherein the control module is further configuredto: upon determining that the A_GSA is compatible with the designatedapproach procedure, allow user input selecting modification of thedesignated approach procedure with the A_GSA.
 13. The system of claim12, wherein the control module is further configured to: subsequent toallowing modification of the designated approach procedure with theA_GSA, receive a user input selecting modification of the designatedapproach procedure with the A_GSA; and modify the designated approachprocedure with the A_GSA.
 14. The system of claim 11, wherein thecontrol module is configured to determine that the A_GSA is notcompatible with the designated approach procedure based on determiningthat employing the A_GSA violates a final approach segment altitudeconstraint.
 15. The method system of claim 14, wherein the data from theon-board sensor system comprises an aircraft position and location, andwherein the control module is further configured to determine that theA_GSA is not compatible with the designated approach procedure based ondetermining that the aircraft position and location violates apredetermined distance from a landing threshold.
 16. The method systemof claim 15, wherein the data from the on-board sensor system furthercomprises an aircraft ground speed, and wherein the control module isfurther configured to determine that the A_GSA is not compatible withthe designated approach procedure based on determining that an amount oftime before landing based is less than a predetermined amount of timebefore landing.
 17. The system of claim 16, wherein the control moduleis further configured to: command the display device to render, a fourthicon indicating whether or not an adaptive interactive glide slope angle(AIGSA) system is activated; a fifth icon indicating an approach type; asixth icon indicating the final approach segment altitude constraint;and a seventh icon indicating whether or not the AIGSA system isactivated.
 18. A method for an approach procedure for an aircraft, themethod comprising: at a control module: receiving, from a user inputdevice, a user designated approach procedure, altitude constraints, andlanding parameters; retrieving, from a navigation database (NDB), thedesignated approach procedure; identifying a designated glide slopeangle (D_GSA) based on the designated approach procedure; receivingsensed weather data and sensed aircraft status data from an on-boardsensor system; determining an adaptive glide slope angle (A_GSA) basedthe sensed weather data and the sensed aircraft status data; processingthe A_GSA with the designated approach procedure to determine whether ornot the A_GSA is compatible with the designated approach procedure; andcommanding a display device to render a user interface comprising aplurality of icons, the plurality of icons comprising, a first iconindicating the D_GSA, a second icon indicating the A_GSA, and a thirdicon indicating whether or not the A_GSA is compatible with thedesignated approach procedure.
 19. The method of claim 18, furthercomprising: upon determining that the A_GSA is compatible with thedesignated approach procedure, allowing modification of the designatedapproach procedure with the A_GSA; and subsequent to allowingmodification of the designated approach procedure with the A_GSA,receiving a user input selecting modification of the designated approachprocedure with the A_GSA; and modifying the designated approachprocedure with the A_GSA.
 20. The method of claim 19, furthercomprising, upon determining that the A_GSA is not compatible with thedesignated approach procedure, generating a first alert and preventingmodification of the designated approach procedure with the A_GSA.
 21. Amethod in an onboard system of an aircraft, the method comprising:retrieving, from a navigation database (NDB), a user selected designatedapproach procedure for the aircraft; identifying a designated glideslope angle (D_GSA) based on the designated approach procedure;receiving sensed data from an on-board sensor system; identifying anadaptive glide slope angle (A_GSA) based on the sensed data; processingthe A_GSA with the designated approach procedure to determine whether ornot the A_GSA is compatible with the designated approach procedure; andcommanding a display device in the aircraft to render a user interfacecomprising a plurality of icons, the plurality of icons comprising: afirst icon indicating the D_GSA, a second icon indicating the A_GSA, anda third icon indicating whether or not the A_GSA is compatible with thedesignated approach procedure.
 22. The method of claim 21, furthercomprising: barring modification of the designated approach procedurewith the A_GSA, when the A_GSA is not compatible with the designatedapproach procedure, and allowing modification of the designated approachprocedure with the A_GSA when the A_GSA is compatible with thedesignated approach procedure.
 23. The method of claim 21, whereindetermining whether or not the A_GSA is compatible with the designatedapproach procedure comprises determining whether or not employing theA_GSA violates a final approach segment altitude constraint.
 24. Themethod of claim 21, wherein determining whether or not the A_GSA iscompatible with the designated approach procedure comprises determiningwhether or not employing the A_GSA, based on an aircraft position andlocation received from the on-board sensor system, violates apredetermined distance from a landing threshold constraint.
 25. Themethod of claim 21, wherein determining whether or not the A_GSA iscompatible with the designated approach procedure comprises determiningwhether or not employing the A_GSA, based on an aircraft position,location, and ground speed received from the on-board sensor system,violates a predetermined amount of time before landing constraint. 26.Non-transitory computer readable media encoded with programminginstructions configurable to cause a processor on an aircraft to performa method, the method comprising: retrieving, from a navigation database(NDB), a user selected designated approach procedure for the aircraft;identifying a designated glide slope angle (D_GSA) based on thedesignated approach procedure; receiving sensed data from a sensorsystem on-board the aircraft; identifying an adaptive glide slope angle(A_GSA) based on the sensed data; processing the A_GSA with thedesignated approach procedure to determine whether or not the A_GSA iscompatible with the designated approach procedure; and commanding adisplay device in the aircraft to render a user interface comprising aplurality of icons, the plurality of icons comprising: a first iconindicating the D_GSA, a second icon indicating the A_GSA, and a thirdicon indicating whether or not the A_GSA is compatible with thedesignated approach procedure.
 27. The non-transitory computer readablemedia of claim 26, wherein the method further comprises: barringmodification of the designated approach procedure with the A_GSA, whenthe A_GSA is not compatible with the designated approach procedure, andallowing modification of the designated approach procedure with theA_GSA when the A_GSA is compatible with the designated approachprocedure.
 28. The non-transitory computer readable media of claim 26,wherein determining whether or not the A_GSA is compatible with thedesignated approach procedure comprises determining whether or notemploying the A_GSA violates a final approach segment altitudeconstraint.
 29. The non-transitory computer readable media of claim 26,wherein determining whether or not the A_GSA is compatible with thedesignated approach procedure comprises determining whether or notemploying the A_GSA, based on an aircraft position and location receivedfrom the on-board sensor system, violates a predetermined distance froma landing threshold constraint.
 30. The non-transitory computer readablemedia of claim 26, wherein determining whether or not the A_GSA iscompatible with the designated approach procedure comprises determiningwhether or not employing the A_GSA, based on an aircraft position,location, and ground speed received from the on-board sensor system,violates a predetermined amount of time before landing constraint.
 31. Acontroller in an onboard aircraft system configured by programminginstructions on non-transitory computer readable media, the controllerconfigured to: retrieve, from a navigation database (NDB), a userselected designated approach procedure for the aircraft; identify adesignated glide slope angle (D_GSA) based on the designated approachprocedure; receive sensed data from a sensor system on-board theaircraft; identify an adaptive glide slope angle (A_GSA) based on thesensed data; process the A_GSA with the designated approach procedure todetermine whether or not the A_GSA is compatible with the designatedapproach procedure; and command a display device in the aircraft torender a user interface comprising a plurality of icons, the pluralityof icons comprising: a first icon indicating the D_GSA, a second iconindicating the A_GSA, and a third icon indicating whether or not theA_GSA is compatible with the designated approach procedure.
 32. Thecontroller of claim 31, further configured to: bar modification of thedesignated approach procedure with the A_GSA, when the A_GSA is notcompatible with the designated approach procedure, and allowmodification of the designated approach procedure with the A_GSA whenthe A_GSA is compatible with the designated approach procedure.
 33. Thecontroller of claim 31, wherein to determine whether or not the A_GSA iscompatible with the designated approach procedure the controller isconfigure to determine whether or not employing the A_GSA violates afinal approach segment altitude constraint.
 34. The controller of claim31, wherein to determine whether or not the A_GSA is compatible with thedesignated approach procedure the controller is configure to determinewhether or not employing the A_GSA, based on an aircraft position andlocation received from the on-board sensor system, violates apredetermined distance from a landing threshold constraint.
 35. Thecontroller of claim 31, wherein to determine whether or not the A_GSA iscompatible with the designated approach procedure the controller isconfigure to determine whether or not employing the A_GSA, based on anaircraft position, location, and ground speed received from the on-boardsensor system, violates a predetermined amount of time before landingconstraint.